feat: restore $schema in plugin.json for spec clients - #112
Merged
Conversation
wangauone
changed the title
wangauone
marked this pull request as ready for review
August 26, 2026 21:45
helloeve
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restores
$schemainplugin.json, so Agent Plugin spec clients recognise the manifest. It was omitted because Codex then read the specmcp.jsonand ignored theenv_varsin.codex-plugin/, leaving user config unforwarded.Codex 0.150.0 removes that constraint: it reads the spec manifest and overlays the
.codex-plugin/env_varsonto the matching servers.Codex 0.150.0 is now stable (released 2026-08-26), so this is safe to merge. Users on 0.149.x and earlier will not get config forwarded to the MCP server until they upgrade.
Verified against the alpha with the
agent-plugin-syncintegration suite: 4/4 harnesses pass on 0.150.0-alpha.11, and the Codex test fails on 0.147.0, which is exactly the behaviour this PR depends on.README also notes the new Codex version requirement. Generated manifests are unchanged, since
$schemadoes not propagate into them.